-
Notifications
You must be signed in to change notification settings - Fork 63
feat: add metadata updates and requirements interface #257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b147683 to
d76a780
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was initially confused about renaming MetadataUpdate to TableUpdate and UpdateRequirement to TableRequirement, but after checking the iceberg-rust and iceberg-python implementations, it now makes sense to me.
|
While I know both WDYT? @Fokko @liurenjie1024 |
Thanks @wgtmac for pinging me. I prefer to add an prefix to improve readability. |
wgtmac
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good. I left some minor comments.
|
Thanks @liurenjie1024 for the input! I think we should stick with the rest catalog api to use |
This commit introduces the metadata update and update requirements system for table metadata modifications.
This commit introduces the metadata update and update requirements system for table metadata modifications.
f737a40 to
4439f8d
Compare
wgtmac
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I've just left a comment w.r.t. class names.
This commit introduces the metadata update and update requirements system for table metadata modifications.